home *** CD-ROM | disk | FTP | other *** search
/ Internet Info 1997 December / Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso / ietf / urn / urn-archives / urn-ietf.archive.9701 / 000020_owner-urn-ietf _Thu Jan 30 01:07:51 1997.msg < prev    next >
Internet Message Format  |  1997-02-19  |  2KB
  1. Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id BAA21126 for urn-ietf-out; Thu, 30 Jan 1997 01:07:51 -0500
  2. Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.10/8.6.9) with SMTP id BAA21121 for <urn-ietf@services.bunyip.com>; Thu, 30 Jan 1997 01:07:47 -0500
  3. Received: from acl.lanl.gov by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b)
  4.         id AA11178  (mail destined for urn-ietf@services.bunyip.com); Thu, 30 Jan 97 01:07:45 -0500
  5. Received: from montana (transitory20.lanl.gov [128.165.7.180]) by acl.lanl.gov (8.7.3/8.7.3) with ESMTP id XAA02743; Wed, 29 Jan 1997 23:07:29 -0700 (MST)
  6. Message-Id: <199701300607.XAA02743@acl.lanl.gov>
  7. From: "Ron Daniel Jr." <rdaniel@lanl.gov>
  8. To: "Keith Moore" <moore@cs.utk.edu>, "Tim Berners-Lee" <timbl@w3.org>
  9. Cc: "Keith Moore" <moore@cs.utk.edu>,
  10.         "Daniel LaLiberte" <liberte@ncsa.uiuc.edu>,
  11.         "Martin J. Duerst" <mduerst@ifi.unizh.ch>,
  12.         "URL mailing list" <ietf-url@imc.org>, <urn-ietf@bunyip.com>
  13. Subject: Re: [URN] Re: Relative URLs and URNs 
  14. Date: Wed, 29 Jan 1997 18:54:23 -0700
  15. X-Msmail-Priority: Normal
  16. X-Priority: 3
  17. X-Mailer: Microsoft Internet Mail 4.70.1155
  18. Mime-Version: 1.0
  19. Content-Type: text/plain; charset=ISO-8859-1
  20. Content-Transfer-Encoding: 7bit
  21. Sender: owner-urn-ietf@services.bunyip.com
  22. Precedence: bulk
  23. Reply-To: "Ron Daniel Jr." <rdaniel@lanl.gov>
  24. Errors-To: owner-urn-ietf@bunyip.com
  25.  
  26. Thus spoke Keith Moore:
  27.  
  28. > If we disallow unencoded '/' within URNs for now, we can always add 
  29. > relative URNs later when we understand them better.
  30.  
  31. I couldn't agree more.
  32.  
  33. Encoding '/' is a bit cumbersome, but it is worth it for the potential
  34. gain in the future.
  35.  
  36.